Repository navigation
feat(sensitive): Home Assistant, and the 99→20 rule scoped to the Hue bridge (#134) - #427
Merged
Merged
Conversation
… bridge (#134) Home Assistant joins stacks/sensitive as the first household service behind Caddy: the Container flavour (no Supervisor, no add-ons), an ordinary member of the tier's network with expose: and no ports:, not network_mode: host — discovery is link-local and every device it controls is a VLAN away. Root because the image has no other mode, bounded by cap_drop ALL, a read-only root and two tmpfs mounts; init: false because s6-overlay refuses to be anything but PID 1. Booted so on the monitoring host from the pinned digest: onboarding served, CapEff 0, 316 MiB RSS, 35 tasks; /run has to be exec. configuration.yaml is mounted read-only over the state volume and loads a packages/ directory rather than the UI editor's automations.yaml, whose include fails hard on a file that does not exist. Caddy gets a fixed address on a fixed subnet so trusted_proxies can name it. ADR-0035 scopes the rule ADR-0008 wrote as 99 → 20. Read against the Skids inventory, one device has a local API — the Hue bridge; everything else is reached through a vendor's cloud or not at all — so the pass is 10.0.99.40 → 10.0.20.104:80,443/tcp, the two ports aiohue uses, inserted above Block access to Skids beside the SNMP passes. Skids has no DHCP reservations and its pool holds the bridge's address, so a reservation is the precondition; the rule is created under #404 once trinity exists. The ADR also records the one place the tier steps outside SOPS: Home Assistant writes the credentials it obtains into its own store in the volume, and nothing this repository renders can hand them in. Refs #134, #404, #98, #149. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
3 tasks
…-sensitive-tier-23027c
This was referenced Sep 10, 2026
Gerrrt
added a commit
that referenced
this pull request
Sep 10, 2026
Home Assistant (#427, #134) landed in stacks/sensitive under this branch. Resolved on main's versions: the compose header counts two household services and eight DIFFERENCEs (Paperless-ngx's CPU ceiling and writable root become 7 and 8; its `init: false` lines point at Home Assistant's DIFFERENCE 5), the Paperless block sits after Home Assistant's, Caddy's `make certs` line carries both names, the Caddyfile keeps main's routing preamble with the Paperless block above the catch-all, the secrets template names four keys and Home Assistant's none, and the README merges both services' notes. backup-volumes.sh also gains a sentinel for home-assistant-config — ./.HA_VERSION, read off a boot of the pinned image — because the merged stack's backup would otherwise refuse on that volume. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Gerrrt
added a commit
that referenced
this pull request
Sep 10, 2026
#427 (Home Assistant, the Hue-bridge rule) and #431 (SNMPv3 per poll) each added an ADR-0035 on separate branches and both merged on 2026-09-09, #431 second. check_docs.py's numbering assertion now fails on main and on every PR that merges it. The one that landed second moves, as the check says: the file, its H1, every link and every bare mention that is about SNMPv3. The Hue-bridge references stay at 0035. README's ADR count goes to 36. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> (cherry picked from commit 06d0e77)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #134 (left open: the rule and the deploy wait on #404). Related: #404, ADR-0032, ADR-0019.
What this adds
stacks/sensitive/: Home Assistant as the third service and the first household one — Container flavour,expose:only, behind Caddy athomeassistant.matrix.elysium. Notnetwork_mode: host, notprivileged: discovery is mDNS/SSDP and link-local, and every device it controls is on Skids, a VLAN away.cap_drop: [ALL],no-new-privileges, read-only root, two tmpfs mounts,init: false(s6-overlay refuses to be anything but PID 1 — measured), 1 GiB ceiling.home-assistant/configuration.yamlmounted read-only over the state volume; automations are YAML inpackages/, not the UI editor, because!include automations.yamlfails hard on a file this repository does not ship.http.trusted_proxiesnames Caddy, which now has a fixed address (172.28.99.2) on a fixed subnet for that one line.99 → 20row ADR-0008 wrote. Read againstnetwork.md's Skids table, one device has a local API —bifrost, the Hue bridge. Ring, the Echos, the HomePods, the litter robot and the Tuya machine are cloud or nothing. So the pass is10.0.99.40 → 10.0.20.104:80,443/tcp(80 foraiohue's pairing probe, 443 for everything after — read from the code), inserted above Block access to Skids beside the SNMP passes.network.md,security.mdandroadmap.mdcarry it as decided, not created./config/.storage; nothing rendered from SOPS can hand them in. The ADR,compose.yaml,security.md's Secrets section andsecrets/sensitive.example.yamlall say so and say what protects them instead.What was measured
morpheus, 2026-09-09: Winterfell's Block access to Skids sits above its egress pass with the three SNMP/HTTP passes above it, so the rule is an insertion, as the roadmap said. Skids has zero DHCP reservations and a.100–.200pool holding every device on the segment — the Hue bridge is at.104by lease. A reservation is the precondition ADR-0035 puts before the rule.compose.yamlhardening on an internal Docker network: onboarding served in ~20 s,CapEff 0for PID 1 and the HA process, 316 MiB RSS, 35 tasks, zero read-only errors. Two findings kept in the file:/runmust beexec(Docker's tmpfs default isnoexec; s6 stages its binaries there), and thedhcpdiscovery integration logs oneOperation not permittedline per start wantingCAP_NET_RAW— it would sniff nothing on a bridge a VLAN from every device, so the capability stays dropped and the line is documented as expected.make validatepasses locally (the three skips are the usual not-the-deploy-checkout ones);pin-digestsagrees with the digest;caddy validateandcaddy fmtpass on the new route.Left for #404 (and why #134 stays open)
bifrostat10.0.20.104— the first on Skids.--dns homeassistant.matrix.elysiumontrinity's leaf and a host override onmorpheus; both commands are in the stack README.Security review
docs/firewall-claims.yamlchanges: the wholesale posture is untouched.secrets/*.sops.yaml— none is added; the one class that cannot is recorded in ADR-0035 rather than papered over.docs/network.mdwith an OUI-truncated MAC — no new device; no coordinator or bridge is needed.🤖 Generated with Claude Code